-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch lifecycle to avoid interacting with project boards overly #375
Conversation
This is a test comment from running CI. Please ignore |
This is a test comment from running CI. Please ignore |
04046a4
to
49f73b5
Compare
This is a test comment from running CI. Please ignore |
Apologies for the messy dangerbot actions -- I refactored lifecycle.py to use GraphQL, but then split that out into a separate PR #377. This is now just a bandaid patch to try to get datasets submitted before #377 can get merged. We will have to manually move the card to the Error cycling to get that to trigger, I believe. |
The passing CI run was triggered manually here: https://github.com/openforcefield/qca-dataset-submission/actions/runs/10807416097/job/29978159402 |
I think this is now ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks for updating this and apologies that this held up submissions!
Thanks for the review @j-wags! |
This PR patches lifecycle.py to give up on moving things between board columns and just submit the datasets. It's meant to be a temporary, easier to review fix than #377.